Log in to ask questions, share your expertise, or stay connected to content you value. Don’t have a login? Learn how to become a member.
It already does the job it needs to do, so it will keep on doing it. 01 version 1.1; 02 03 ns junos = "http://xml.juniper.net/junos/*/junos"; 04 ns xnm = "http://xml.juniper.net/xnm/1.1/xnm"; 05 ns jcs = "http://xml.juniper.net/junos/commit-scripts/1.0"; 06 07 import "../import/junos.xsl"; 08 09 match configuration ( 10 /* Insert code here */ 11 ) As you can see, the only actual change is a shift in the version number from 1.0 to 1.1. The namespaces stay the same, the import statement stays the same, and the starting template remains match configuration. Because of this commonality with the SLAX 1.0 boilerplates, commit scripts that follow the 1.1 boilerplate behave in the same way as those that follow the 1.0 boilerplate: Initial context node is /commit-script-input/configuration
Use the check-ldp Script to Enforce LDP-IGP Consistency For SLAX version 1.0 and higher, you can use the check-ldp script to enforce enforce LDP - IGP consistency
This page also compares/contrasts the SLAX 1.1 boilerplate against the SLAX 1.0 boilerplate. #FAQ #event-script #Slax
This page also compares/contrasts the SLAX 1.1 boilerplate against the SLAX 1.0 boilerplate. #Slax #eventandOPscripts #How-To
You can also compare and contrast this boilerplate with the boilerplate for SLAX 1.0. #commitscript #How-To #Slax #JunosOS
This applies to SLAX version 1.0 and higher
Configure Any Interface with 'Core' in Description with MTU Length For SLAX version 1.0 and higher, you can use this commit script to check that any interface with "CORE" or "core" in the description is configured with an MTU of 4484 (in this example)